home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Belgian Amiga Club - ADF Collection
/
BS1 part 41.zip
/
BS1 part 41
/
Schematic CAD v1.9.adf
/
Docs
/
Changes
< prev
next >
Wrap
Text File
|
1989-01-02
|
10KB
|
205 lines
*****************************************************************************
Changes record for Scheme(tm) to Ver 1.9
*****************************************************************************
Charles B. Blish, N4EJI, for SoftCircuits, Inc.
Imported and also spread out by QUARTEX in 1989
*****************************************************************************
V1.0:
(from Beta levels) Scheme has been differentiated into two individual
products. Scheme and SchemePlus. Scheme is the current release, and
SchemePlus will be an enhanced version of this product, compatible
at the file level. SchemePlus is planned for release in the summer of
1988.
The object editor specifications windows have been removed, as
Scheme will only support objects on a drawing basis. SchemePlus will
support drawings with additional specification and other rule checking,
as well as other features yet to be implemented.
Plot program has been provided.
Save and load of objects has been activated.
File format is now frozen, Schematics may be created without
any fear of loss due to file compatability problems... if there are
any changes in the file format, conversion utilities will be supplied
as required to support the user community.
UnDo is now activated as well.
Framework layer has been removed as not required.
V1.1:
Added Screen Print facility, allowing any Amiga printer that handles
graphics to print out schematics from Scheme.
V1.2:
Default palette selection now actually reloads the default.config
file, if there is one... instead of setting up _lousy_ colors...
You can now drag objects, live, in an intuitive fashion. Entire
groups of objects can be moved via this technique; Although only one
object will actually drag, any object that is selected will "snap"
to the same relative position after a move or copy is specified
from a drag operation. If no move or copy is specified, then the
dragged image will dissapear the next time the screen is redrawn.
V1.3:
Bug Fix: Undo interaction with delete objects would trash drawing
in some situations. Fixed.
V1.4:
Bug Fix: UnDo interaction with WorkSpace/Clear_Objects would trash
drawing in some cases. Fixed.
SetPri tool added to relase disk, for use in changing the system's
operating characteristics; specifically intended to make sure that
Scheme does not hog the CPU when things like comm programs are running.
Due to a strangeness in the Amiga's system software, only tasks that
were started from the CLI will show up / be settable from SetPri...
so if you want to use this tool, make sure that whatever you want
to adjust was started from the CLI.
*** NOTE: New SetPri works on BOTH WB and CLI tasks - see notes for
v1.8
V1.5:
Added IFF screen save function so schematics can be passed around the
amiga community and viewed with paint programs, slideshows, etc.
IFF images, at this time, are NOT compressed; this means that a 64k
file is created when you save an IFF screen from Scheme. Compression
may be added at a later date. In the meantime, loading an image saved
by Scheme into any paint package (such as DPaint II (c) Electronic Arts)
and then saving it again will make it a compressed file.
IFF screen save was also added to PCLOplus at this time. (pclo+ V1.7)
V1.6:
Added mark group function, in both menu and gadget palette.
Rectangular lasso style interactive mark.
V1.7:
Added verification requester to Save Object and Save Drawing operations.
These operations would rewrite your original file without asking, and
were determined to have too much hazardous potential in certain
situations. The addition of the requester, though adding some extra
steps to what is intended to be a quick operation, makes it a safe
feature.
V1.8:
Bug in Object Save routine fixed; some users experienced problems
when saving objects. Fixed.
Bug in yes/no requester routine fixed: Caused text to be clipped at
the edge of the requester for some messages
Bug in object editor that allowed you to specify zero length lines
has been removed; problem was that you could palce such a line, but
you could not delete them, as two clicks upon the same point was
interpreted as a request to delete a node, not a line
The filerequester window would sort once before actually reading
the target directory; this could take several seconds in the case of
a large directory. It now sorts only after a directory read, IF the
sort or sortlock gadgets are activated.
Window bounds have been expanded slightly to allow you some more
room at the edges of the drawing. Every little bit...
Changed operation of the text/object gadget
Added ReDraw menu, subitems - provides control to user of when redraws
occur - use with caution!
Bug: Modified plot output routine: Objects that fell completely off
of the screen when the plot output file was generated were not sent
to the output plot file - fixed.
Starting with this revision, Scheme is being compiled with the
Lattice v4.0 'c' compiler; this results in faster, smaller code -
good for you, good for us. In addition, this results in a smaller
'chip' ram requirment, allowing you to run more programs in your
system. That is due to the ability of the lattice compiler to
be very specific about which variables go where in the system. Only
variables that _require_ chip ram are placed there - others are
placed in fast ram, if available.
The drawing routines have been reworked to take advantage of the
new compiler capabilities, resulting in approximatly 30% faster
screen redraws.
New version of SetPri tool provided - this version has several changes
that make it much nicer to use; First, it doesn't open that little
'extra' window on the screen when run from wb; Second, and more
importantly, it shows workbench tasks as well as CLI tasks.
Scheme's gadgets and menus have been synchronized - All the
menu 'checkmarks' and gadget images are now correct and 'in sync'
with each other, even if the gadget palette is disabled during menu
select operations.
The delete operation, when initiated from the menus, did NOT delete
selected wires. It will now.
The delete operation deleted marked objects BEFORE it deleted
marked wires - this had the effect of forcing you to execute
TWO delete operations if marked objects were attached to marked
wires - the object delete would fail the first time because there
were wires attched, then the wires would be deleted; then, when you
pressed delete the second time, the objects would go, because they
no longer had wires attached. To remedy this, wires are now
deleted first; then objects can be freed before the delete attempt
is made and they will get deleted on the first try.
IMPORTANT NOTE:
There is a BUG in this release (and previous, at least in v1.7 that
we're sure of) that MAY appear when you are editing a schematic;
This bug has the effect of causing wires to snap to objects that
they do NOT belong to; these wires are impossible to select by
the normal means, and connectable points on some objects may also
become inaccessable; We have NOT found the bug; as mentioned, it only
occurs very rarely... what we have done, until we can get a handle
on the actual problem (more on that in a bit) is provide a function
that can positivly identify any items in the drawing that are affected
with this problem... the function 'selects' any object and/or wire
that it identifies as having rouge nodes, and you can completely
repair your drawing by selecting the DELETE operation either in
the gadget palette or the select menu. We didn't make it delete
them for you because you will want to make a note of which items
have the problem so you can replace them properly.
You initiate the verify function by pressing the 'v' key... if there
are no problems, a requester indicating this appears. The operation
of the function is very fast - there will be no delay incurred by
using it other than clicking on the OK button in the requester.
We suggest that you use the function often!
If it DOES find a problem, a requester will be brought up that
indicates an object number, and the number of problem items found
for that object, as well as the total number of problem items
found so far... take note of how many items these requesters
indicate to you, so that you are sure to find any that might be
offscreen but still selected. Please also take the time to write
down the object number(s); If you can isolate the sequence of
operations that causes the problem, it is likely that this may
be of some aid to us in debugging the problem.
Again, it should be emphasized that the problem is rare, and you
may never see it, even with heavy use of the program: If you do,
it is relativly painless for you to fix.
IF YOU CAN ISOLATE A SEQUENCE OF OPERATIONS THAT *CAUSES* THIS
PROBLEM, PLEASE REPORT SAME TO SOFTCIRCUITS IMMEDIATELY SO THAT
WE CAN KILL THIS ANNOYING BUG! Thank you!